Issues pertaining to CMS application

1. Validation of Running Allowance document ver 1.17

2. Validate Slate running document Ver1.1 for Centre Railway

3. Automatic signaling Competency due date

Alternative I

Alternative II

Due date is after 6 months as per G&SR (SR para 9.08(3))

NR is following 1 year as per their SR

Facility has been provided where division can be configured for either alternative I or alternative II.

4. Payment of Incentive for routes with plain and ghat section (freight)

Route A-B-C, A-B plain 100 km with min gurantee, B-C ghat 50 km with off
		Alternative I		Alternative II
Criteria	Calculation		Mileage	Calculation	Mileage
Actual	100 + 50		150	100 + 50	150
Apply incentive	Only on 100 (ghat section km not to be considered) (NIL as < 126)		150 (150 + 0)	On 150 (ghat section km to be considered) (20% as 126<150<175)	180 (150 + 30)
Apply Ghat (say type I = 5 times which means Km + 4 times Km)	50*4 (5-1)=200		350 (200 +150)	50*4 (5-1)=200	380 (200 +180)
Check minimum	350 >120, not applicable		350	380 >120, not applicable	380
Calculate off	On 50 (50*.15 = 7.5)			On 50 (50*.15 = 7.5)
Grand Total	350 + 7.5		357.5	380 + 7.5	387.5

CMS is following Alternative I. Please confirm if alternative II is to be followed.

(Ghat section km shall not be considered for incentive calculation as ghat section incentive is applied to ghat section and further consideration of this will lead to double incentive.)

5. Payment of Incentive for routes with plain and ghat section (Coaching)

Route A-B-C, A-B plain 113 km with min gurantee, B-C ghat 12 km with off, Run duration 6 hrs
		Alternative I		Alternative II
Criteria	Calculation		Mileage	Calculation	Mileage
Actual	113 + 12		125	113 + 12	125
Apply Ghat (say type I = 5 times which means Km + 4 times Km)	12*4 (5-1)=48		173 (125 +48)	12*4 (5-1)=48	173 (125 +48)
Apply incentive	(5 hrs and above actual subject to min of 150) On 150 NIL as mileage is 173		173 (173 + 0)	(5 hrs and above actual subject to min of 150) On 125 150 as actual is 125 which is < 150	198 (150 + 48)
Check minimum	173 >120, not applicable		173	198 >120, not applicable	198
Calculate off	On 12 (12*.15 = 1.8)			On 12 (12*.15 = 1.8)
Grand Total	173 + 1.8		174.8	198 + 1.8	199.8

CMS is following Alternative I. Please confirm if alternative II is to be followed (Only RNC division is asking for Alternative II)

(Ghat section km shall be considered for incentive calculation as incentive is based on time and minimum mileage. Since minimum mileage exceeds the limit specified for that time period extra km will imply double incentive.)

6. Effect of reducing rostered hrs for non run days and giving credit for non run days for OT calculation due to differential rate

Fortnight	14 days
Rostered hrs	104 hrs / 96 (for shunter)	7 hrs 26 min (7.428 hrs) per day 6 hrs 51 min (6.857 hrs) per day for shunter	RB Letter no E(LWA) 66 HER 42 dt 17-11-1966, Sl no ER6569/SE439/66
	Alternative I	Alternative II	Alternative III
No of days on duty (Working + Rest)	8	8	8
Working hrs (say)	76	76	76
Non Run period (excluding absent) (say Leave)	5	5	5
Non Run Period (Absent)	1	1	1
Credit for Non run days (wherever admissible) (In case crew was on leave for 4 days and absent on 1 day credit will be given for 4 days and not 5)	Give credit for 5 days (7 hrs 26 min) 7.428 * 5 = 37.14	Reduce rostered hrs lower limit proportionately = (104/14)*5 = 37.14 hrs (37 hrs 8 min) Effective Rostered hrs 104 – 37.14 = 66.86 (66 hrs 51 min) Rounded off = 67 hrs	Reduce rostered hrs lower limit proportionately = (104/14)5 = 37.14 hrs (37 hrs 8 min) Effective Rostered hrs 104 – 37.14 = 66.86 (66 hrs 51 min), rounded off = 67 Reduce rostered hrs upper limit proportionately = (108/14)5 = 38.57 hrs (38 hrs 34 min) Effective Rostered hrs 108 – 38.57 = 69.42 (69 hrs 25 min) rounded off = 69 hrs
Total duty hrs for fort night	76 + 37.14 = 113.14 rounded off = 113 hrs	76	76
Total OT hrs	113 – 104 = 9 hrs	76 – 67 = 9 hrs	76 – 67 = 9 hrs
Over time hrs at higher rate for duty hrs > 108	113 – 108 = 5 hrs	NIL as all values less than 108 hrs	76 – 69 = 7 hrs
Over time hrs at lower rate for duty hrs > 104 but < 108	108 -104 = 4 hrs	76 – 67 = 9 hrs	69 – 67 = 2 hrs

CMS is following alternative I. (earlier Alternative II was followed). Alternative III to be followed.

(Both the alternative will give same result if there is no differential rate of over time.)

7. First Available First Out (FAFO) vs First In First Out (FIFO)

FIFO is actually FIFA for the case given below otherwise it is same

Crew	Sign off time	Duty hrs performed	Available after	Available At
A	1500 hrs	> 8 hrs	16 hrs	0700 hrs
B	1600 hrs	< 8 hrs	12 hrs	0400 hrs

If crew is ordered after 0700 hrs Order in which crew will be displayed will be

Though crew A was IN first, but displayed as no 2 in order of availability.

CMS is following above.

CMS by default follows FAFO. Option has been provided to configure independently each division to follow FAFO or FIFO on request.

( There is very little difference in both the options except for rare typical cases hence facility to configure the criteria as FIFO or FAFO at Divisional level is acceptable.)

8. Fetch Crew by Rule v/s Fetch Crew all

	Criterion	Fetch Crew By Rule	Fetch Crew All with LR check	Fetch Crew All

1	PME	Y	Y	Y
2	REFT	Y	Y	Y
3	TRACTION	Y*	Y*	Y*
4	ROUTE LEARNING (LR)	Y*	Y*	N
5	SAFETY CAMP	Y	N	N
6	LOCO COMPETENCY	Y*	N	N
7	REFE	Y	N	N
8	REFD	Y	N	N
9	AUTOMATIC SIGNALING COMPETENCY	Y*	N	N

‘*’ Depending on details in Traffic Advice (TA)

Exceptions for following Service type

Service type	Instead of	Check
MEMU	REFE	MEMU TRG#
EMU	REFE	EMU TRG#
DMU	REFD	DMU TRG#

# These are one time training only with periodicity not specified. Presently periodicity of 3 yrs is being followed.

Exceptions demanded for Shunter (Eastern Railway)

No training from above list including

PME

REFT

As per FIFO list of all crew satisfying above criteria in order of their time of availability (first in & rest completed) is displayed for booking (Under rest crew is also displayed in different colour,). Supervisor can book any crew appearing in the list thus displayed over ruling the order of the list, after giving reason for the same.

Requirement to dispense with certain criteria for booking of crew was envisaged to be used in extreme conditions. E.g. Trains to be run on diverted route in case of flood accident etc.

However Railways have been doing large no of booking following fetch crew all option.

( However exceptions for shunters are not acceptable. Medical and refresher traffic are must requirement from the point of view of physical fitness and basic operational competence, hence cannot be dispensed with.)

9. Visibility of circulars

Alternative I	Alternative II
Circular created by lobby are visible to crew of that lobby at HQ and even at other lobby (Outstation lobby)	Circular created by lobby are visible to crew of that lobby at HQ and even at other lobby, in addition circular of other lobby are also available to OS crew signing ON and that lobby

CMS is following Alternative I. Please confirm if alternative II is to be followed.

( Alternative I shall be followed as a crew can go to lobbies in more than one division also. If he is required to read all the circulars of all the divisions

He has to read a large no of circulars and assimilate them
All the circulars have to be read before he can sign ON)

10. Back Reporting

Alternative I	Alternative II
CMS allows back reporting till crew ‘sign ON’ on the system	CMS allows back reporting till crew sign ON even after crew has signed ON and performed other duties
	This may create problem in calculation of mileage and other reports as duties being filled later may change the mileage for the duties which have already been captured in the system. e.g. continuous run
	LR updation will be affected. The count for no of trips required for LR will be disturbed.
	In case staff being booked as per their progressive hours, this will cause a change in the booking disturbing earlier bookings
	A large no of procedures are fired to update database tables daily at predetermined time / event. All the data entries will be affected.
	Major changes in application will be required as the flow of application is changing drastically

CMS is following Alternative I. Alternative II is not recommended. Possibility of manual data entry for all subsequent duties again with back reporting can be explored. For example say data has been captured till 10^th of month and then from 15^th to 25^th of the month. Now on 25^th if back reporting for a period from 10^th to 15^th is required, manual data entry will be required from 10^th to 25^th instead of 19^th to 15^th.

( Post facto change needs to be verified for mandatory requirements like PME and REFT and RDT etc. and pervious duty details, and at the same time will affect all the runs after the change as well, hence not recommended.)

11. Result awaited

Alternative I

Alternative II

Crew once sent on some non run reason (refresher training etc.) requires result of the training available to bring him back from non run and utilize him for duty.

· Crew to be allowed to be brought back from non run with result status as awaited.

· Crew will be allowed to work normally if due date is not over.

· In case due date for that non run reason is over crew will be allowed to be utilized with restriction depending upon type of training for which result is awaited.

CMS is following Alternative II with the release of ver 3.8.0 (earlier Alternative I was followed).

( results shall be given at the end of course before departure of crew for HQ.)

12. Mileage for mail exp crew utilized for freight operation

Alternative I	Alternative II
Mail Exp crew is permitted for Freight (through manual data entry only) and mileage calculation is done as per Freight rules. Benefits applicable for freight crew e.g. km based incentive are applicable.	Mail Exp crew is allowed to be booked for Freight (through manual data entry only) and mileage calculation is done as per Freight rules but without the benefit of incentive etc.

CMS is following Alternative I. Please confirm if alternative II is to be followed.

(Since crew is being utilized in freight service, benefits of freight service shall be payable to crew.)

13. Automatic bringing back crew from non run

Alternative I

Alternative II

Crew is brought back from the non run by the supervisor (normally after crew has reported at lobby as per the practice pre CMS days) even if expected date and time of arrival is provided in the non run.

Crew to be brought back automatically out of non run where expected date of arrival is available with the system.

crew will be back automatically at 23:59 hrs.

CMS is following Alternative II for all non run reason with the release of ver 3.8.0. (Earlier Alternative I was followed for all non run reason except leave where alternative II was followed)

( Earlier crew was required to report to the lobby and only then he was treated as available. With increasing distance and increase in means of communication, there is no need for the crew to report to lobby. Where expected date of arrival is available crew should automatically be made available at the start of the day. Whether crew shall be booked from odd hours or after night hrs (0600 hrs) or any other pre defined hr, needs to be reviewed separately.)

14. Authority to ‘sign ON’ on behalf of crew

Alternative I

Alternative II

Only lobby where crew has signed off is authorized to make crew status as sign ON. Through manual data entry. In case if crew could not sign ON at the lobby due to non availability of CMS application (network or power problem), Crew can sign OFF at destination only after entry for sign ON has been made by the starting lobby.

This required lobby to sign ON on behalf of crew by obtaining his password.

Provision for lobby supervisor to sign ON on behalf of crew in his absence with mandatory declaration by supervisor for the following.

Supervisor will be asked to confirm the following for sign ON to take place

please conform the following

· crew has read the circular

· crew is carrying glasses

· crew has passed the BA test

· Crew is carrying personal mobile (if yes, give the no and service provider)

· Reason for sign ON by supervisor

· I take the reponsibility for crew sign ON

Form will display all other fields being displayed on Kiosk at the time of sign ON
This sign ON will automatically mean sign ON approval

CMS was following Alternative I. Alternative II provided with release of version 3.10.0.

There is additional demand that in addition to the sign off lobby, divisional control to be permitted to do ‘sign ON’, on behalf of crew.

( For the reasons beyond the control of lobby such as network failure, power failure, system failure etc. there is need to send the crew without signing on in the system. Since supervisor has to ensure that necessary safety precautions have been taken before crew can perform the duty, supervisor shall be allowed to ‘sign on’ on behalf of crew after necessary certification.)

15. Route distance

Alternative I	Alternative II
While creating new routes inter station data is picked up from RBS database. (Earlier FOIS database). Inter station distances than can be edited from CRIS in presence of representative from user lobby.	No change is permitted in the inter station data picked up from RBS database. (Earlier FOIS database)
Mileage is corrected as per the practice and requirement of user lobby	Mileage will not be as per user requirement and will lead to non usage of CMS application
Interstation distance for the same station in different routes can be different	Inter station distance will always be as per FOIS data.

CMS is following Alternative I. Please confirm if alternative II is to be followed.

(No change in RBS data shall be permitted. In case a discrepancy is observed there is need to correct the RBS data and route data be reconciled from RBS data only)

16. Route creation

Alternative I

Alternative II

Only CRIS is authorized to create new route or edit new routes as per requirement of user lobby in the presence of representative of user lobby

Div control / Lobby to be authorized to create and edit routes

Editing of routes data is not frequent and some control is available

Routes may be edited and created frequently with out any control.

This may lead to error in mileage calculation and also creation of unnecessary redundant routes.

CMS is following Alternative I. Please confirm if alternative II is to be followed.

(Creation of routes at lobby level will lead to creation of multiple routes even if existing routes can serve the purpose and is not recommended. Creation of superfluous routes will load the data base also)

17. Spare by road (Ahemdabad)

Present system

Additional requirement

Crew signing on at station A performing duty from station B for freight, crew may go from A to B as spare either by rail or by road

CMS system gives mileage from A to B, for spare working based on rail distance even if crew goes by road.

A new duty type option of spare Rd required, which will give fixed mileage km to be filled at the time creating TA, and also at the time of manual data entry for crew going as spare by road.

CMS is following Alternative I. Please confirm if additional facility as alternative II is to be followed.

(The existing practice of mileage as per railway route even if crew is being sent by road may be followed for uniform practice.)

18. Clarifications of rule regarding Coal Pilot

A. CMS system for calculation of Coal Pilot mileage is working at present as per logic below

· “For all coal pilot working Base station is defined and corresponding to base, coal pilot sidings are defined.

· The base station can be a lobby station or even a non lobby station.

· Crew Sign ON at Lobby and goes

o Lobby -à base station -à siding

o Siding -à Base Station -à Lobby

· Crew Sign OFF at Lobby on return

· Duty hrs starts from Sign ON at lobby to Sign OFF at lobby

· Mileage for Lobby to base station & base station to Lobby is normal freight mileage.

· From base station to siding,

o Predefined mileage (km ) is given as configured for that siding

o Bonus km as configured for that siding are added if crew perform journey from base to CP siding and returns back to base with in pre defined time as configured.

B. Coal Pilot working is handled through manual data entry only, as time of arrival and departure at base station cannot be captured being NCMS point

C. Requirement to include calculation of mileage for the following type of working has arisen as under:

a. If crew goes from Base station to Coal pilot siding 1 and then proceed to another Coal pilot siding 2 and then come back to base station. There is no rule to attach two or more than two siding to a single base station

b. If crew goes from Base station to Coal pilot siding and does not return to base or proceed to other lobby.

c. Clarification of rule regarding above 2 points is requested. This can be handled by making fixed mileage routes for all such possible working at present.

D. Coal pilot for Private siding (Bilaspur)

Present system; Alternative I

Additional requirement: Alternative II

Crew signing on at station A then doing coal pilot duty for a siding (available in FOIS)

Pre configured mileage for that siding paid. Two values are configured for each siding based on duty hrs from Sign ON to Sign OFF at the base lobby.

Crew to work from FOIS siding to one private siding then come back to main siding and go to another private siding without coming back to base lobby.

FOIS Siding is non CMS point so there is no way to record no of trips to individual pvt. siding. Can be done through manual data entry but will require pvt. siding to be defined in FOIS and configuring mileage and bonus for each pvt. siding etc.

E. New set of rules has been defined for the coal pilot working. A new Module has been developed which will be visible to only those lobbies which are pre configured for coal pilot working.

a. SET to be defined instead of individual run

b. SET can consist of one or more than one run

c. Bonus km and bonus hrs will be applicable to SET

d. TA will be made for coal pilot with SET to be indicated in route

e. Sign ON and Sign OFF will be done at KIOSK with option to change the SET.

f. After sign OFF flow will be directed to new manual entry (different from existing manual entry)

g. In case crew does not sign OFF at kiosk same can also be handled through new manual entry. In this case sign OFF time will required to be filled.

h. All runs will now be pre populated with set details with following changes permitted while saving

· Opt for new set

· Loco no/Type, Train No, for individual run

· Arr. Dep. time for individual run

19. Good shed working at the same station (Bilaspur)

Present system: Alternative I

Additional requirement: Alternative II

Presently hrs based mileage is given only to the shunter.

Provision is available for creation of yard at the same station, so that crew having suitable yard learning is selected at the time of linking

Shunting to be performed at the same station with bonus km in addition to hrs based mileage

Now the yard should be configurable for additional bonus km. (similar to coal pilot siding)

Crew if working on these yard(goods shed) will get additional km in addition to hrs based mileage (at present).

Km based mileage is given for freight / coaching

CMS is following Alternative I

(There is no provision of giving bonus km for shunting in a particular yard. Such local aberrations shall not be permitted.)

20. Non standard out station rest

Lobby are free to configure following rest arrangements

TYPE	Duty Hrs	Rest at HQ	Rest at Outstation
Type I	< 8 Hrs	12 Hrs Rest	2/3rd of the duty performed
Type I	>= 8 Hrs Duty	16 Hrs Rest	8 Hrs Rest (Staff may opt for 6 Hrs rest)

Type II	< 5 Hrs < = < 5 Hrs = <	12 Hrs Rest	Actual duty Hrs + 1 Hr
	>= 5 to < 8 Hrs	12 Hrs Rest	6 Hrs
	>= 8 Hrs Duty	16 Hrs Rest	8 Hrs Rest (Staff may opt for 6 Hrs rest)

Type III	< 8 Hrs	12 Hrs Rest	½ of the duty performed
Type III	>= 8 Hrs Duty	16 Hrs Rest	8 Hrs Rest (Staff may opt for 6 Hrs rest)

Type IV	<8 Hrs	12 Hrs Rest	1 + Hrs Duty Performed
Type IV	>= 8 Hrs Duty	16 Hrs Rest	8 Hrs Rest (Staff may opt for 6 Hrs rest)

Type V	< 8 Hrs	12 Hrs Rest	4 Hrs
	= 8 Hrs Duty	16 Hrs Rest	4 Hrs
	> 8 to < 10 Hrs	16 Hrs Rest	6 Hrs
	>= 10 Hrs	16 Hrs Rest	8 Hrs

Please indicate if required to be standardised for IR

21. Non standard periodicity of monitoring

Lobby are free to configure following periodicity

Crew Gradation \Counseling	Type-I	Type-II	Type-III	Type-IV	Type-V	Type-VI
A	60 Days	90 Days	3 years	1year	½Years	3Years
B	30 Days	60 Days	2Years	1year	½Years	2Years
C	15 Days	30 Days	½Years	1year	½Years	1Years
D	NA	NA	NA	NA	NA	NA

Alert to be given if crew is in category D, “You are booking D category crew”

Please indicate if required to be standardised for IR.

( standardisation of periodicity for Indian Railways. Crew graded ‘D’ shall not be permitted for booking on running duties and shall be reviewed after 30 days.)

22. Rest for shunter

· There is no pre defined rest for shunter between two consecutive duties.

· A shunter can be booked without any rest in the last shift of day 1 and first shift of day 2

· No BOR is payable as rest is not defined.

(fresh rules to be drafted for shunting duty covering

a) Maximum duty hrs in a day

b) Minimum rest hrs between two shunting shifts

c) Breach of rest allowance for shunters

d) Maximum night hrs in a week)

23. Non Standard Shunting Duty hrs (Kurla)

Mileages should be calculated on 8 hrs shift whereas OT shall be paid after 9 hrs of working such that after

· 108 Hrs instead of 96 Hrs (as is the case for other lobbies) for shunters

· 108 Hrs instead of 104 hrs (as is the case for other lobbies) for LPG used on shunting.

Shunting hours duty ceiling of 240 hrs

· Port Shuttling: Min 160Km, Hrs of duty (rounded OFF- Rule2) x 20, max limit 200 Km (240 km for Kurla lobby CLA)

( standard rules to be followed for all the lobbies across Indian Railways. However considering historic reasons for Kurla Lobby existing practice may be permitted till consensus is arrived.)

24. New designation for loco pilot ghat (Kurla)

· Requirement is to designate particular crew as LPG Ghat in Bio-data. There is no authorized designation as Loco Pilot Ghat. All functions will remain same as Sr LPG. These crew will appear as LP Ghat in Reports only. Does not affect Mileage statement.

(standard rules to be followed for all the lobbies across Indian Railways. However considering historic reasons for Kurla Lobby existing practice may be permitted till consensus is arrived.)

25. Special Mileage (Adra)

a. Pay 120 km upto 60 km

b. Pay 3 time km beyond 60 km

c. The above mileage is to be paid for any route on authority no 505/506 from Sr DOM

d. In CMS mileage will be actual km in non min guarantee section and 120 km in min guaranteed section.

e. This will again require a special duty type. Once selected user will be asked to give authority no and date.

f. No other mileage (ghat, minimum guarantee, incentive etc.) will be payable over and above the mileage explained above.

g. Since new option will be available at all lobby points, lobbies need to be alert not to use it if not permitted at their lobby.

(standard rules to be followed for all the lobbies across Indian Railways. Local aberrations like this shall not be permitted.)

26. PRIME Integration

a. PRIME is a d2k based decentralized system hosted at divisional level.

b. PRIME fields are not uniform across the railways

c. CMS reports can be exported to Excel format directly (Facility available only after Stage I) which can then be arranged to suit export to PRIME in soft form.

d. PF field is available, data to be filled in crew biodata for it to appear in report.

e. License free Software image is under procurement and will be provided by Feb 2012. This will provide facility for exporting reports to EXCEL format

f. Railways have been demanding conversion of allowance payable directly into money value. Allowance payable were not being converted into money value till now for following reasons

i. Conversion of allowance to money value was not in the scope of originally approved System Requirement Specification (SRS)

ii. Calculation of money payable was with Personnel branch.

iii. Clearance for incorporating officiating allowance has been given recently.

iv. Continuous evolution of Use case specification for Running allowance

v. Need for mileage statement based on Use case specification for Running allowance to stabilize.

vi. Railways are still paying AMA differently

vii. Conversion of mileage statement and over time statement to money value can be taken up only after approval of Use case specification for Running allowance proper authorization from CAO/ FOIS

g. PRIME is being replaced by a centralized web based system IPAS “Integrated Prime & Afres System”. IT would be prudent to integrate CMS with centralized IPAS subject to approval for converting mileage to money value.

26.1. Present status:

a. CMS system provides for generating and downloading following .txt file

i. mileage for all crew

ii. mileage for LP (SLP, LPP, LPM)

iii. mileage for ALP (SALP)

iv. mileage for guards

b. Format of txt file as on date is as under.

CREW_ID	(8)
EMPLOYEE_NO	(8)
PF_CODE	(16)
Pay Period	(6) (YYYYMM)(MONTH SLOT START DATE)
Mileage	(5)
ALKM_NON_LEAVE	(2)
ALKM_LEAVE	(2)
RRA	(4)(IN DECIMAL FORM(XX.X))
BOR	(3)
NDA	(3)
NHA	(2)
SHUNT_COUNT	(2)
CREW_CADRE	(1)
NAME	(30)
DHRS	(3)
RUN_KM	(5)
OFF1_KMS	(5)
OFF2_KMS	(5)
NON_KM	(4)
TRIP_COUNT	(2)~~(ALL DATA PREFIXED BY '#')~~
OSRA	(5)
OVER_TIME	(3)
LOW_OT	(2)
HIGH_OT	(3)
NO_OF_PROG_SLOT_IN_MONTH	(1) (ALL DATA PREFIXED BY '#')

milsum Example:

#TKD1681################20090482201407#1839#4#9#0.0##0#45#1#0E##########MUKESH#KR#SRIVASTAVA206#1839####0####0###0#0##250#80#5#753

c. File has also been provided with SQL script to directly insert the values in PRIME Database (Oracle)

milsumsql Example:

INSERT INTO MILEAGE_SUMMARY_PRIME VALUES('TKD1681','','20090482','201407',1839,4,9,0.0,0,45,1,0,'E','MUKESH KR SRIVASTAVA',206,1839,0,0,0,0,250,80,5,75,3);

27. Batch printing

a. Crew wise, crew run detail for each run (details as per JTR/CTR) as well as non run are available.

b. Railways are printing the same and sending it to personal department. This document for a crew requires around 4 pages to be printed per crew. Lobbies have been provided with dot matrix printer assuming printing of only monthly mileage summary.

c. All the reports are also available on Internet (Not requiring FOIS connectivity)

d. Decision is required if these reports are to be printed and kept in hard copy.

( ~~printing~~(Printing of crew movement detailsis not recommended to avoid wastage of paper. Facility is available with in CMS to export the data to excel format. Only soft copy of records shall be kept.)

28. Thin Client v/s PC for CMS

A. CMS application is running on 24X7 basis, being used by low skilled staff, requires reliable and simple equipment at user end with least user intervention.

B. CRIS recommends use of Thin Clients as lobby TSS equipment for the reasons explained below.

1. Low initial cost

2. No moving part (Fan less design, no hard disk for better reliability)

3. Low power consumption

4. Low memory requirement (ROM instead of Hard drive, being more reliable)

5. Client software with Highly customized linux OS for

a. Low memory requirement

b. Client use restricted to CMS application only

c. Preconfigured setting for browser, resolution, printer etc. requiring no user intervention (user is not required to launch the application, do any setting, load drivers etc. User has limited access to change the setting and even if these are disturbed, restarting the machine loads the original setting))

d. Remote management and remote configuration. (Resetting is possible from CRIS)

e. Easy validations while accessing CMS application.

f. Less prone to virus attack

C. Following constraints were observed in maintenance of Linux based thin clients

1. Difficulty in arranging maintenance resources for linux based thin clients

2. Non availability of license free customized linux OS with client application

3. Limited supplier for thin client with required client image (Customised linux OS + app)

4. User wanted to use PC with windows, for the browser based CMS application.

5. Drivers for BA and Bio devices were readily available for windows.

D. Problems with use of PC

1. Less reliable due to moving parts like cooling fan and hard drive

2. More prone to virus attack

3. Difficulty in remote assistance

4. Difficulty in validations in accessing CMS through standard browser. (Procurement of windows application by CRIS and access to CMS through CMS client application will resolve issues like validation and further facilitate use of PC.)

E. Practical experiences indicate that restricted environment of thin client provides, is easy to resolve from CRIS. How ever such flexibility may not be there in PC with more open environment. It is difficult to restrict user access in PC

F. CRIS plans for the development of CMS client for Linux OS and Windows in order to address the points outlined in (B) above. Objective was to have a ready proprietary image of CRIS which can be used at client location.

1. Customised Linux OS with client application for lobbies using thin client with drivers for BA, Bio Metric and Printers

2. Application for Windows for lobbies using PC with drivers for BA, Bio Metric and Printers. Though CRIS preferred use of Thin client with customized OS and application image.

G. The client application shall be with following features (both for Linux as well as windows)

1. Standard customised Linux desk top shall appear at initial set up. Customised Linux OS shall be hardware neutral i.e. it shall work for Intel / AMD / VIA based client machines.

2. Client application shall be separate from OS and appear as desktop icon after initial loading. (Both for coustomised Linux, standard linux and windows desktop)

3. With the launch of client application, the client machine shall be configured as desktop client or kiosk client depending on IP address configured in CMS system, It shall also be possible to configure the client manually (locally) in case of no connection to CMS central server. Remote manual setting option shall also be available.

4. Once client application is launched, the client machine shall always boot up as configured above, till brought out to desk top (initial set up) through hardware key combination. (say Ctrl + alt +F1)

5. Client application shall be suitable for

a. Windows Platform : Windows 7 / Embedded windows XP / Windows 8 or latest version of Windows to be launched in year 2012

b. Linux Platform: Customised Linux / Fedora / Red Hat /Ubuntu

6. Customised Linux OS shall support standard commercially available peripherals like 80 /132 column dot matrix printer / inkjet printer / laser printer / line printer, web cams, scanners, multifunction devices etc.

7. It should be possible to load drivers locally and even over the network for new standard devices and CMS specific devices like BA equipment, Bio metric devices.

8. It is expected that drivers for these devices will be available for windows platform from the OEM itself. However, drivers for such devices for Linux need to be developed by the vendor.

9. Initially drivers for at least two commercially available standard BA devices and two Bio devices are proposed to be provided with the client application.. These drivers shall get loaded through the client application itself. It may be required to develop drivers for Linux for devices of other makes introduced at a later stage.

H. Use of PC shall be preferably be resorted, with windows based CMS client application only, which is available on pen drive.

29. Km & time for sending to non run

a. Crew gets a preconfigured mileage for attending non run duties at outstation.

b. However there is no provision for transit time for going to non run station. Crew is either in rest or in non run reason and not in transit for non run.

c. Crew gets allowance once for going to the out station and once for coming back from out station. However if crew is sent from one non run to other without getting back to base station no mileage is paid.

30. Provision for CTR edit option

CTR edit option cannot be provided for following reasons

a. Mileage calculation procedure runs daily at fixed schedule (presently at 02.00 hrs), and mileage gets calculated over IR In case edited data requires previous/ subsequent run to change from continuous or discontinuous or vice versa it will disturb the mileage calculation which will give random errors.

b. Subsequent to each run many tables in data base are updated for other parameters such as rest, progressive hrs, competencies etc. It may not be feasible to apply changes inter related in nature, across the application.

c. More over further operation / logical decisions has already been committed based on present parameters which can not be undone.

d. Fortnightly report, OT statement etc. will vary from mileage report data.

(facility to edit run details once saved for the reasons explained above is not recommended).

31. Shunting hrs on enroute stations other than starting and terminating station.

a. Presently Crew at the time of sign OFF can select a station enroute (3rd from starting and last but one) he is required to select shunting enroute and fill the station , shunting order and date, for getting shunt count

b. Now he can select first or last station and will be required to enter shunting order no and hrs of shunting, for hrs based shunting

c. A count will be given for each entry in mileage (3rd to last but one station) and shunting mileage @15 km / hr will be given for hrs (hr:min) entered (for starting and terminating station, rounded off as per existing rule)

d. There is no rule to provide shunting hrs for any station except staring and terminating station in main line working.

32. Printing of caution order

a. CMS provides facility to feed the caution order for the division.

b. Divisional authority feed caution order between two adjacent stations for the section where caution is to be observed.

c. Caution can also be fed for the same station for caution to be observed within station limits.

d. Caution order is displayed for the route selected. All sections / stations on the selected route are picked up for display.

e. ASM also generates CO independently.

f. Print facility has not been given as Caution order is to be delivered to crew under signature of ASM. Printing of CO through CMS will lead to duplicity and ambiguity.

(Authority for printing of caution order at multiple location being a safety issue is not recommended).

33. Sending on non run on the day of sign OFF

Present system	requirement
Alternative I	Alternative II
Leave
Leave to be granted on the same day if Sign OFF + Rest (12/16 hrs) is before 12:00 hrs	Leave to be granted on the same day if Sign OFF is before 12:00 hrs
Leave to be granted on the next day if Sign OFF + Rest (12/16 hrs) is after 12:00 hrs	Leave to be granted on the next day if Sign OFF is after 12:00 hrs

Non run other than Leave e.g. Training, Absent, Sick
Non Run to be granted from the time of sending to non run subject to sending time > Sign OFF time	NO Change Non Run to be granted from the time of sending to non run subject to sending time > Sign OFF time

CMS is following alternative I

Muster roll

if sign OFF on the same day as non run

Status = W / Non Run reason

if sign OFF on the previous day as non run

Status = Non Run reason

if sign OFF on the same day as non run

Status = W

if sign OFF on the previous day as non run

Status = Non Run reason

CMS is following alternative I. (earlier Alternative II was followed)

( Rest period shall not be curtailed for giving leave as it affects safety. Giving extra rest hours is safer.)

34. Time for call serve through SMS during rest hours

· Crew name appears in the availability list if the Train departure time in the Traffic Advice (TA) is after completion of rest of that crew.

· The SMS for call serve is generated at the time of booking of crew on that TA.

Alternative I	Alternative II
SMS for call serve can be delivered to crew prior to completion of rest depending upon time of booking.	SMS for call serve shall be delivered only after completion of rest hrs.
	crew can be booked only on those trains for which train departure time is 2 hrs. after completion of rest as normally two hrs. notice is required for call serve.
	In this case crew rest time will automatically be extended by 2 hrs. beyond prescribed rest hrs.
	This will also require that crew shall be booked immediately after being available and no advance booking will be possible

(Sending an SMS during rest hrs shall not be treated as disturbance in rest. Rather it facilitates crew to plan better.)

35. Bifurcation of officiating and non officiating mileage

Logic for Bifurcating Total Calculated Mileage under none officiating, officiating of type 1 and officiating of type 2.

Total mileage for officiating of type 1	Footplate km + Officiating Incentive (15% of Footplate Km)
Total mileage for officiating of type 2	Footplate km + Officiating Incentive (15% of Footplate Km)
Total mileage under non officiating	Total calculated mileage - Total mileage for officiating of type 1 - Total mileage for officiating of type 2

Example:

Cont duty: Working(off1) + Working(off2)	Cont duty: Working(off1) + Working
Min Guarantee	Min Guarantee
Case I Crew goes working A – B (90 km) Rests at B < 1 hr (cont duty) and goes working B – C (140 km) Mileage :- 90+140 =230 Incentive: - 92(@40%) Total = 322 km which is > 120 km Mileage provided = 322 + 13.5(off1) + 21.0(off2) =356.5 km Mileage under Officiating1 =90 +13.5 = 103.5 Mileage under Officiating2 =140 +21.0 = 161.0 Mileage under Non Officiating = 356.4 – 103.5 – 161.0 = 92	Case I Crew goes working A – B (90 km) Rests at B < 1 hr (cont duty) and goes working B – C (140 km) Mileage :- 90+140 =230 Incentive: - 92(@40%) Total = 322 km which is > 120 km Mileage provided = 322 +13.5(off1) = 335.5 Mileage under Officiating1 =90 +13.5 =103.5 Mileage under Non Officiating = 335.5 -103.5=232
Case II Crew goes working A – B (40 km) Rests at B < 1 hr (cont duty) and goes working B – C (50 km) Mileage :- 40+50 =90 Incentive: - 0 Total = 90 km which is < 120 km Mileage provided = 120 + 6.0(off1) + 7.5(off2) =133.5 km Mileage under Officiating1 = 40 + 6.0 = 46.0 Mileage under Officiating2 = 50 + 7.5 = 57.5 Mileage under Non Officiating = 133.5 46.0 – 57.5 = 30	Case II Crew goes working A – B (40 km) Rests at B < 1 hr (cont duty) and goes working B – C (50 km) Mileage :- 40+50 =90 Incentive: - 0 Total = 90 km which is < 120 km Mileage provided = 120 + 6 (off1) =126km Mileage under Officiating1 = 40 + 6 = 46 Mileage under Non Officiating = 126 - 46 = 80

Working other then DUTY_TYPE = WR considered as non officiated working for mileage calculation

(Bifurcating min guarantee mileage in the ratio of footplate km is not recommended as it amounts to double advantage.)

36. Permission to officiate

Each crew type has a natural service type where he can work without off
Crew can work for permitted OFF (1) or OFF(1.15) designation as per table below only after he is made officiating from Biodata
Service type are allowed as per designation permitted for officiating OFF(1) as well as (OFF 1.15) (table below)

CREW TYPE	SERVICE TYPE	OFF(1)	OFF(1.15)
CREW TYPE	SERVICE TYPE	OFF(1)	OFF(1.15)
LPG	FGHT	SHT,SSHT	LPP,SLPP,LPM
SLPG	FGHT	SHT,SSHT,LPP,SLPP	LPM
LPP	PASSENGER (CCHP)	SHT,SSHT,LPG,SLPG,SLPP	LPM
SLPP	PASSENGER (CCHP)	SHT,SSHT,LPG,SLPG,LPM
LPM	MAIL/EXP (CCHM), RAJDHANI (CCHR), HIGH SPEED (CCHS)	SHT,SSHT,LPG,SLPG,SLPP
ALP	FGHT, PASSENGER (CCHP), MAIL/EXP (CCHM), RAJDHANI (CCHR), HIGH SPEED (CCHS)		SHT,SSHT,LPG,SLPG
SALP	FGHT, PASSENGER (CCHP), MAIL/EXP (CCHM), RAJDHANI (CCHR), HIGH SPEED (CCHS)	SHT,SSHT	LPG,SLPG
GD	FREIGHT		GDP,SGDP,GDM
SGD	FREIGHT	GDP,SGDP	GDM
GDP	PASSENGER (CCHP)		GDM
SGDP	PASSENGER (CCHP)	GDM
GDM	MAIL/EXP (CCHM), RAJDHANI (CCHR), HIGH SPEED (CCHS)
SHT		LPP,SLPP	LPG,SLPG
SSHT		LPG,SLPG,LPP,SLPP

Crew once made officiating for a particular designation higher than his original designation out of permitted designations in OFF(1) and OFF(1.15) will be allowed to officiate in lower designation as per table below till his original designation. But if he is permitted in lower designation then he can officiate in his original designation and only in the lower officiated designation

Officiating order Loco
officiated designation	LPM	SLPP	LPP	SLPG	LPG	SSHT	SHT	SALP	ALP

Officiating order Guard
officiated designation	GDM	SGDP	GDP	SGD	GD

(crew in higher grade shall not be permitted to officiate in lower grade. However considering the shortage of crew all over Indian Railways, the existing practice as detailed above may be allowed for the time being.)

37. Rounding off in continuous run for hours based mileage

Alternate I	Alternate II
Rounding off on individual duty hrs	Rounding off after combining duty hrs in continuous run
Case I	Case I
Duty 1: Shunting 5 hrs 20 min Rest: 50 min (< 1 hour) Duty 2: Shunting 5 hrs 15 min	Duty 1: Shunting 5 hrs 20 min Rest: 50 min (< 1 hour) Duty 2: Shunting 5 hrs 15 min
Mileage 1: (5 hrs 20 min rounded off as 5 hrs) 5 X 15 = 75 Mileage 2: (5 hrs 15 min rounded off as 5 hrs) 5 X 15 = 75 Total Mileage = 75 + 75 = 150 Total Duty hrs = 10 hrs 35 min + 50 min = 11 hrs 25 min	Total Working hrs = 10 hrs 35 min Rounded off = 11 hrs Mileage: 11 X 15 = 165 Total Duty hrs; 10 hrs 35 min + 50 min = 11 hrs 25 min
Case II	Case II
Duty 1: Shunting 5 hrs 40 min Rest: 50 min (< 1 hour) Duty 2: Shunting 5 hrs 35 min	Duty 1: Shunting 5 hrs 40 min Rest: 50 min (< 1 hour) Duty 2: Shunting 5 hrs 35 min
Mileage 1: (5 hrs 40 min rounded off as 6 hrs) 6 X 15 = 90 Mileage 2: (5 hrs 35 min rounded off as 6 hrs) 6 X 15 = 90 Total Mileage = 90 + 90 = 180 Total Duty hrs = 11 hrs 15 min + 50 min = 12 hrs 05 min	Total Duty hrs = 11 hrs 15 min Rounded off = 11 hrs Mileage = 11 X 15 = 165 Total Duty hrs; 10 hrs 35 min + 50 min = 11 hrs 25 min

CMS is following alternative I

(Rounding off will introduce one or other type of error whatever scheme is followed. Over a period of time such errors will average out.)

38. Minimum Guarantee Rules

38.1. User definable hrs. (X’ hrs interval) for declaring a run CONTINUOUS in minimum guarantee section

Two runs are treated as CONTINUOUS if time interval from Sign OFF from first run to sign ON of second run is <= 1 hrs. for all types and sections
Present system	requirement
Two successive run on the same min guarantee section with a break of > 1hr (non continuous duty) , minimum guarantee is applicable independently for both the run	Two successive run on the same min guarantee section with a break of > 1hr (X hrs)(non continuous duty) , minimum guarantee is applicable only once
Section A - B 90 km , crew goes working from A to B , rests at B > 1hrs, come back from B - A Mileage as per Run A to B = 90 km Mileage given = 120 km, being minimum gurantee section Mileage as per Run B to A = 90 km Mileage given = 120 km, being minimum gurantee section TOTAL MILEAGE GIVEN = 240 km	Section A - B 90 km , crew goes working from A to B , rests at B > 1hrs, come back from B - A Mileage as per Run A to B = 90 km Mileage given = 120 km, being minimum gurantee section Mileage as per Run B to A = 90 km Mileage given = 120 km, being minimum gurantee section TOTAL MILEAGE GIVEN = 120 km

CMS is following Alternative I.

As per some Railways concept of continuous run should not be applicable in case of minimum guarantee section.

38.2. Special rates for minimum guarantee section (Delhi Area)

Delhi follow three tier structure for minimum guarantee section
Section A – B = a km (min guarantee) Crew goes working A – B Rests at B < 1 hr (cont duty) and returns spare B – A or does shunting at B Mileage A – B = a km Mileage B – A = b km
If	Give
a + b < 80 km	120 km
80 km < a + b < 160 km	160 km
a + b > 160 km	a + b

38.3. Combination of two Continuous run, working + working, in Minimum guarantee section

As per RB directive a section may be defined as minimum guarantee section if sections and circumstances do not have potential for running staff to earn adequate kilometerage within stipulated duty hrs.
Cont duty: working + working	Cont duty: Working + working
Alternative I	Alternative II
Apply check to the total mileage
Case I Section A - B = 90 km , (min Guarantee section) crew goes working A - B , rests at B < 1hrs (continuous duty) come back working B - A Mileage A – B = 90 km B – A = 90 km Total = 180 km > 120 Mileage given = 180 km, as mileage earned is more than mileage of minimum guarantee section	Case I Section A - B = 90 km , (min Guarantee section) crew goes working A - B , rests at B < 1hrs (continuous duty) come back working B - A Mileage A – B = 90 km B – A = 90 km Total = 180 km Mileage given = 120 km, being minimum guarantee section
	Section needs to be redfined
Case II Section A - B = 40 km , crew goes working A - B , rests at B < 1hrs (continuous duty) come back working B - A Mileage A – B = 40 km B – A = 40 km Total = 80 km < 120 Mileage given = 120 km, as mileage earned is less than mileage of minimum guarantee section	Case II Section A - B = 40 km , crew goes working A - B , rests at B < 1hrs (continuous duty) come back working B - A Mileage A – B = 40 km B – A = 40 km Total = 80 km Mileage given = 120 km, being minimum guarantee section

CMS is following Alternative I.

38.4. Combination of working + spare, working + shunting in Minimum guarantee section

Old System	Present System
In case of continuous run no mileage will be given for Shunting duty / spare duty type (For Freight only) if minimum guarantee is applicable.	In case of continuous duty (such that rest at other station < 1 hrs) spare mileage to be given even if minimum guarantee applicable Shunting duty type will have no change Ref Railway Board letter no E (P&A) II- 85 / FE -4/3 dated 25-05-1985
Case I Section A - B = X km , (min Guarantee section) crew goes working A - B , rests at B < 1hrs (continuous duty) does spare B- A or shunting at B mileage earned Y km
Option I	Option II
Working + spare	Working + spare
If (X + Y) < 120 mileage given = 120 If (X + Y) > 120 mileage given = (X + Y)	Mileage given = 120 + Y (no check to be performed for X + Y)
Working + shunting	Working + Shunting
If (X + Y) <120 mileage given = 120 If (X + Y) > 120 mileage given = (X + Y)	Mileage given = 120 + Y (no check to be performed for X + Y)
Working + shunting (Delhi area)
If (X + Y) < 80 mileage given = 120 If (X + Y) > 80 but < 160 mileage given = 160 If (X +Y) > 160 mileage given = X + Y

Note : In case of Delhi Area if Working(X), spare (Y) and Shunting (Z) are in continuous duty, check will be performed on (X + Y + Z)

Examples:

Cont duty: Working + spare	Cont duty: Working + spare
Option I	Option II
Case I Section A – B = 90 km (min guarantee) Crew goes working A – B Rests at B < 1 hr (cont duty) and returns spare B - A Mileage A – B = 90 km Mileage B – A = 45 km Total = 135 km which is > 120 km Mileage provided = 135 km	Case I Section A – B = 90 km (min guarantee) Crew goes working A – B Rests at B < 1 hr (cont duty) and returns spare B - A Mileage A – B = 90 km Mileage given = 120 km (min gurantee) Mileage B – A = 45 km Total = 165 km
Case II Section A – B = 40 km (min guarantee) Crew goes working A – B Rests at B < 1 hr (cont duty) and returns spare B - A Mileage A – B = 40 km Mileage B – A = 20 km (spare) Total = 60 km which is < 120 km Mileage provided = 120 km.	Case II Section A – B = 40 km (min guarantee) Crew goes working A – B Rests at B < 1 hr (cont duty) and returns spare B - A Mileage A – B = 40 km Mileage given = 120 km (min gurantee) Mileage B – A = 20 km (spare) Total = 140 km
Default	WR, SER
Cont duty: working + shunting	Cont duty: Working + shunting
Case I Section A - B = 90 km , (min Guarantee section) crew goes working A - B , rests at B < 1hrs (continuous duty) does shunting at B for 5 hrs Mileage A – B = 90 km Mileage given = 120 B = 15 X 5 = 75 km Total = 195 km
Case II Section A - B = 40 km , crew goes working A - B , rests at B < 1hrs (continuous duty) does shunting at B for 5 hrs Mileage A – B = 40 km Mileage given = 120 km B = 15 X 5 = 75 km Total = 195 km
	Delhi Area
	Case I Section A - B = 90 km , (min Guarantee section) crew goes working A - B , rests at B < 1hrs (continuous duty) does shunting at B for 5 hrs Mileage A – B = 90 km B = 15 X 5 = 75 km Total = 165 km > 80 and > 160 Mileage given = 165 km, as mileage earned is more than mileage of minimum guarantee section
	Case II Section A - B = 40 km , crew goes working A - B , rests at B < 1hrs (continuous duty) rests at B < 1hrs (continuous duty) does shunting at B for 5 hrs Mileage A – B = 40 km B = 15 X 5 = 75 km Total = 105 km > 80 but < 160 Mileage given = 160 km, as mileage earned is less than mileage of minimum guarantee section
	Case III Section A - B = 40 km , crew goes working A - B , rests at B < 1hrs (continuous duty) rests at B < 1hrs (continuous duty) does shunting at B for 2 hrs Mileage A – B = 40 km B = 15 X 2 = 30 km Total = 70 km < 80 (and also < 160) Mileage given = 120 km, as mileage earned is less than mileage of minimum guarantee section

CMS proposes to follow Alternative I as default. However divisions can be configured independently for either of alternative.

38.5. Combination of, working + shunting in Minimum guarantee section, (with shunting at intermediate station and not at originating or terminating station)

Requirement of Dhanbad Section A – B – C = (min guarantee) A – B = a km B – C = b km Crew goes working A – B Rests at B < 1 hr (cont duty) and goes spare B - C
Alternative I		Alternative II
Run	Mileage	Run	Mileage
A - C	120 km	A – C	120 km + b
Dhanbad interpretation If spare duty is performed with in the specified minimum guarantee section, spare mileage will not be added over and above minimum mileage, but if spare duty is performed before or after complete run of minimum guarantee section only then spare mileage will be added over and above minimum guarantee mileage.

Note: CMS proposes to follow alternative II

38.6. Minimum guarantee in ghat section

Route A-B total km = 90 (minimum guarantee) , with 20 km of type I ghat
		Alternative I		Alternative II		Alternative III
Criteria	Calculation		Mileage	Calculation	Mileage	Calculation	Mileage
Actual	90		90	90	90	90	90
Apply Ghat (say type I = 5 times which means Km + 4 times Km)	20*4 (5-1)=80		170 (90 +80)	20*4 (5-1)=80	170 (90 +80)	20*4 (5-1)=80	170 (90 +80)
Check minimum	170 >120, not applicable		170	90 <120, hence applicable	200 (120+80)	90 <120, hence applicable	200 (120+80)
Apply incentive	Only on 70 (ghat section km not to be considered) (NIL as < 126)		170 (90 + 80)	On 170 (ghat section km to be considered) (30% as 150<176<200	251 (200 +51)	On 200 (ghat section km to be considered) (40% as 176<200	280 (200 + 80)

Note: CMS follows alternative I with minimum check is applied after incentive (CKP wants alternative III)

39. Weightage for calculating mileage

Calculation will be independent for each service type e.g. freight and coaching

	Other than coaching	Coaching
1	Actual	Actual
2	Incentive (based on KM) on actual (relevant portion excluding ghat)	Incentive (based on hrs of duty) on actual + Ghat (relevant portion)
3	Ghat on actual (relevant portion)	Ghat on actual (relevant portion)
4	Minimum on above total	Minimum on above Total
5	Officiating on actual (relevant portion)	Officiating on actual (relevant portion)
6	Grand total with off

It may be noted that if the order for application of various weightage is changed the mileage will also change. This is self evident from various examples in the document. Many iossues are result of different scheme being followed by different Railway.

(Uniform scheme shall be followed across the Railway for uniformity in mileage calculation.)